chore: fix JavaScript lint errors (issue #11559)#11571
Merged
kgryte merged 1 commit intostdlib-js:developfrom Apr 19, 2026
Merged
chore: fix JavaScript lint errors (issue #11559)#11571kgryte merged 1 commit intostdlib-js:developfrom
kgryte merged 1 commit intostdlib-js:developfrom
Conversation
Replace three `new Array( len/8 )` + zero-fill-loop patterns with an empty array-literal plus `push` loop in `lib/node_modules/@stdlib/assert/has-sharedarraybuffer-support/test/test.js` to satisfy the `stdlib/no-new-array` rule. The Mock() helpers produce identical output; only the allocation strategy changes. Resolves stdlib-js#11559
stdlib-bot
added
Needs Review
Contributor
Coverage Report
The above coverage report was generated for the changes in this PR. |
kgryte
added
difficulty: 1
kgryte
approved these changes
Apr 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #11559.
Description
This pull request:
stdlib/no-new-arraylint errors thatstdlib-botflagged in the 2026-04-19 daily JavaScript lint workflow run:lib/node_modules/@stdlib/assert/has-sharedarraybuffer-support/test/test.js:64,138,164.out = new Array( len/8 ); for (...) out[i] = 0;pattern inside theMock( len )helpers without = []; for (...) out.push( 0 );. Same final array (zero-filled, lengthlen/8), same downstream property assignments (out.byteLength,out.slice). Only the allocation strategy changes.Related Issues
This pull request has the following related issues:
Questions
No.
Other
grep -n "new Array" lib/node_modules/@stdlib/assert/has-sharedarraybuffer-support/test/test.jsreturns no matches after the change.Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
This PR was generated with Claude Code, which applied the three identical
stdlib/no-new-arrayrefactors verbatim after the author confirmed each code section matched the pattern flagged by the bot-filed issue.@stdlib-js/reviewers